Magazyn Enter 2000 February

home *** CD-ROM | disk | FTP | other *** search

/ Magazyn Enter 2000 February / enter2_1.iso / UZYTKI / lotus organizer / CG7QUNA.EXE / readnet.txt < prev next >

Wrap

Text File | 1999-09-15 | 28KB | 694 lines

Installing Lotus Products on a Network Server ---------------------------------------------------------------------- This file contains information for systems administrators who are installing Lotus products to be shared by multiple users locally or across a network. Contents of this file: 1. Sharing Lotus Application Among Multiple Users 2. Why Use a Lotus Application on a Network? 3. Supported Networks 4. Overview of a Network Installation 5. How to Install on a File Server 6. How to Install on a Network Node 7. Creating Personal Directories 8. Creating Shared Data Directories 9. Automated Install 10. Uninstall 11. Information to Give Users 12. If You Have a Problem 13. Network-Specific Information for Organizer 14. Multilingual Install --------------------------------------------------- 1. Sharing Lotus Applications Among Multiple Users --------------------------------------------------- Lotus applications can be installed in a variety of ways for your users. Standard Install: This installs the product to each user's hard disk. This installation is best for users who do not want to rely on server access to run applications. Lotus Install runs a Standard Install by default unless you select the File Server or Multiple users install checkbox in the Welcome dialog box. Distribution Install: This install copies the contents of the Lotus diskettes or a CD-ROM to a network file server. You can then use the copy on the server to perform subsequent standard, file server, or distribution installs. This installation is useful if you will be running several standard installs for users who are at least occasionally connected to the network. You can run Install for them from the distribution location on the server rather than having to bring the diskettes or the CD-ROM to their machine. You access Distribution Install by selecting the File Server or multiple user install checkbox in the Welcome dialog box of the Lotus Install program. File Server or Multiple User Install: Lotus applications can be configured to be shared by multiple "node" users. The main portion of the applications will reside in one location and all node users will be configured to use the applications from that location. All users must have access to this shared location via a network or on a local machine. To share a Lotus application across a network, select the File Server or Multiple User Install checkbox in the Welcome dialog box of the Lotus Install program and then select a network drive as the installation destination. You must then run Node Install from this location for each node user. To share a Lotus application among multiple users on one machine, select the File Server or Multiple User Install checkbox in the Welcome dialog box of the Lotus Install program and then select a local or network drive as the installation destination. You must then run Node Install from this location for each user while logged into the machine as that user. Select a unique personal directory for each node user (such as c:\users\user1\lotus) and do not overwrite your server install (for example, c:\lotus) when you run the node installs. Note: In addition, by default, Windows 95 does not enable separate multiple user settings on a machine. To enable this feature in Windows 95, run the Passwords applet in the Control Panel, select the User Profiles tab, select the "Users can customize their preferences..." radio button and select all the User Profile Settings checkboxes. Node Install: Node Install configures users to run the Lotus application from a shared location. Such users are called node users. Node Install prompts for the location of personal directory for that node user. A personal directory is used for user data files, application configuration files, node user features such as personal copies of SmartMasters. Personal directories can be on a local or network drive. -------------------------------------------- 2. Why Use a Lotus Application on a Network -------------------------------------------- The benefits of using Lotus applications on a network include: * Conserve hard disk space by having only one copy of a Lotus application on the file server instead of a copy on each personal computer. * Allow users to share files, computer equipment, printers, backup devices, and other networked resources. * Quickly distribute files, templates, and applications while users access files immediately. * Back up files centrally. * Save time when upgrading to a new release of a Lotus application, because you upgrade the software on the file server instead of on individual computers. ---------------------- 3. Supported Networks ---------------------- Lotus supports the following networks. Artisoft LANtastic versions 6.0 and 7.0* Banyan VINES version 6.0** DEC PATHWORKS version 5.1 and later OS/2 LAN Server 4.0 and IBM Warp Server Microsoft Windows NT Server version 3.51 or later Novell NetWare versions 3.x and 4.1 * LANtastic 7.0 not available in time for sufficient testing ** Universal Naming Convention (UNC) paths are not supported adequately under existing Banyan 6.0 client. Contact Banyan for potential updates. -------------------------------------- 4. Overview of a Network Installation -------------------------------------- You must complete the following tasks to install a Lotus application on a file server. 1. When upgrading from a previous release of a Lotus application, copy files that you want to save to another directory before erasing the program files from your server. 2. Determine the location and names of the server directories. We recommend that you use the directory structure shown here: Main Lotus directory (\LOTUS) Program directory - Organizer 6.0 (\LOTUS\ORGANIZE) Shared Component directory (\LOTUS\COMPNENT) Note: If you decide to install Lotus applications to different areas on the network, and if these applications will be used by the same node users, make sure you only have one shared components directory on the network for these users. 3. Decide whether to use Universal Naming Convention (UNC) or drive letter mapping. UNC specifies a server name and volume or sharename in the format \\server\volume. Drive mapping associates a letter with a server and volume and directory for easy access. Install records its settings based on how you run install. If you install to the server using a UNC path, node users must also use UNC paths when running node install. This means that the server and volume specified must always be available. If you install to the server using a drive letter path, node users must be mapped to all Lotus product and shared tools directories on the file server at the same level in the directory structure as you specify during the file server install. 4. Use the Lotus Install program to install the Lotus application on the server. 5. Create any personal or shared data directories on the file server. 6. Make printers and network directories available to users. 7. (Optional) Create a batch file, or update the system or user login script, to connect users to network directories. 8. Give users the information listed in section 11, "Information to Give Users," of this document. ----------------------------------- 5. How to Install on a File Server ----------------------------------- To run a File Server Install: 1. Insert the CD-ROM or Diskette 1 into the appropriate drive. 2. Choose Start, then Run from the taskbar. 3. Enter X:\LOTUS\INSTALL in the Run dialog box, where X: is your CD-ROM drive or floppy. 4. On the Welcome dialog box, select the File Server or Multiple User checkbox. Install consists of a series of dialog boxes that are generally self-explanatory. If you need more information when using a dialog box, choose Help by clicking the Help button or pressing ALT+H. When running Install: * Use the Node User Feature Access dialog to specify whether node users can copy any product features to their personal directory. (The features are available to node users whether they can copy them or not.) You must choose "Customize features" in the Install Options dialog box to access the Node User Features dialog box. * After you install a Lotus application on the file server, you must run a Node Install for each user before the user can run the application. Node Install sets up up personal directories for node users. During Node Install, node users can choose which of the Node User Features you selected during Server Install to install to their personal directory. * Please keep in mind that if you are not installing to a UNC path, node users must be mapped to all Lotus product and shared tools directories on the file server at the same level in the directory structure as you specify during the file server install. * If your node users run a shared copy of Windows 95 located on a file server (rather than having Windows 95 on their own machines), you must run the Server Install from the same shared copy of Windows 95. When you run a Server Install from a shared copy of Windows 95, the files that Organizer needs which are installed to the \windows\system and \windows\fonts directories are installed to the shared copy of Windows on the file server. A Node Install from a machine that uses a shared copy of Windows will then allow that user to use these files from the shared Windows location. ------------------------------------ 6. How to Install on a Network Node ------------------------------------ Once you have installed a Lotus application on a network file server, the Lotus Node Install program resides on that server. To install the application on a node, you must run a Node Install. NOTE: If you want to run a Lotus application from the file server rather than from a node, you must complete the Node Install on the file server. To run Node Install: 1. Choose Start then Run from the taskbar. 2. Enter X:\PATH\INSTALL in the Run dialog box, where X:\PATH is the drive letter and path for the main Lotus directory of the Lotus application on your file server. 3. Choose OK. NOTE: Please keep in mind that if you are not installing to a UNC path, node users must be mapped to all product and shared tool directories on the file server at the same level in the directory structure as you specify during the file server install. --------------------------------- 7. Creating Personal Directories --------------------------------- Users who run a Lotus application from a file server must have a personal directory. This directory can reside on either the file server or a node, and contains the application configuration files. If you selected features during the file server install that node users could copy, the personal directory contains these also. Users can also store data or other files in their personal directories. NOTE: Users must have a separate personal directory for each Lotus application. When deciding where to locate personal directories, determine if the file server or node has enough disk space for personal directories. Also, the file server may be the more convenient location for personal directories if you are responsible for regularly backing up and archiving data files. If you decide to put personal directories on nodes, let users create them because they are familiar with the directory structure of their hard disks. During installation on a node, Install prompts users for the name and location of their personal directory, and creates the directory if it does not already exist. If you decide to put personal directories on the file server, create the directories yourself, because you must assign network names and access privileges to those directories. ------------------------------------ 8. Creating Shared Data Directories ------------------------------------ Shared data directories contain data files users create. One copy of a shared data file may serve many users. Shared data directories can have any name, can be in any location on the file server, and must be accessible to node users. After you install the Lotus application(s) on the file server, make the server directories available to network users. The procedure differs for each network. However, you generally need to give users read-only access to directories in which you don't want them to write over, delete, or create files; and give each user full access to a personal directory. Additionally, if applicable for your network, make directories shareable by giving the directory location on the server a network name (share name). --------------------- 9. Automated Install --------------------- Automated Install is a feature that allows users to run the Lotus Install program without the user interface. This feature is particularly useful for network administrators who must manage installs and upgrades for large groups of users. You use this feature by filling in the fields in the response file (instorg.rsp), and then making that file available to users. The information you supply in this file provides input to the Install program so it can run without user intervention. NOTE: Only network administrators should edit the response file. Individual users should use the response file provided to them by their network administrator. To use the automated install feature, first prepare the response file: 1. Back up the response file by copying it to a new name (instorg.sav, for example). 2. In the original response file, provide the information for each field. Examine each default value to make sure it is the value you want. Read the comments for each field for information about legal values and possible interactions with other fields. 3. Validate your response file by running an Install that uses the response file as input. (See the command line information below). The Install program displays any errors that occur. Remember that if you are testing Node Installs, you must run a File Server Install first. When your response file has no errors and performs the install as you intend, make it available to your users with instructions about how to run the Install program. You might want to tell them what command line to type, or you might choose a different method. The best distribution strategy depends on the tools available at your site. To run an automated install: 1. Choose Start then Run from the taskbar. 2. Type the install command: <Path>\install /A <ResponseFilePath> [/U ["UserName"]] [/O [<LogFilePath>]] [/?] where: Path is the location of the install program executable. /A turns on the automated install feature. ResponseFilePath is the full path and name of the response file. If you do not specify a path, this defaults to the directory in which your install executable resides. /U allows you to specify the name of the user. "UserName" is the name of the user to which this copy of the program is registered. See the comments for the UserName field in the response file for information about defaults. /O allows you to specify the status log file path and filename. LogFilePath is the full path and name of the status log file. If you do not specify a path, this defaults to \<windowsdir>\lotinst.log. /? brings up the command line usage message. ------------- 10. Uninstall ------------- The Lotus Uninstall program allows you to remove the Lotus application which you installed. You can run Uninstall from the Start Menu. To run Uninstall: 1. Choose Settings - Control Panel from the Start menu. 2. Select Add/Remove Programs. 3. Choose the program to be removed. 4. Click Remove. Network administrators can run an automated Uninstall by using the Uninstall command line. LUNIN11 /T <ProductName> /V <ProductVersion> /I <INF_file_path> /C <CINSTALL.INI_file_path> [/A] [/O [<LogFilePath>]] [/L <LanguageCode>] [/U <UserName>] where: * /T <ProductName> is the product name, exactly as found in the Registry. * /V <ProductVersion> is the product version, exactly as found in the Registry. * /I <INF_file_path> is the the complete path and name of the file that lists the product files. This file always has an .INF extension. * /C <CINSTALL.INI_file_path> is the complete path and name of the install configuration file, CINSTALL.INI. * [/A] causes an automated Uninstall. * [/O [<LogFilePath>]]] specifies the name and location of the message log file Uninstall creates. This file will include a record of each item removed and any error messages encountered. If you omit this parameter, it defaults to LOTUNIN.LOG in the Windows directory. * [/L <LanguageCode>] specifies the language in which Uninstall will run. If you omit this parameter, Uninstall defaults to English. Valid codes are the 2-character ISO standard language codes. You can enter any language code here, as long as you have installed the product in that language on this system. * [/U <UserName>] specifies the user name to place in the Uninstall log file. This parameter is for informational purposes only. If you omit this parameter, Uninstall defaults to the current user. For example, the following Uninstall command line would invoke the English version of Uninstall to remove ABC release 2.1. In this example, the main Lotus directory is called LOTUS, the main product directory is ABC, and the log file will be written to the root of C instead of the Windows directory. LUNIN11 /T ABC /V 2.1 /I C:\LOTUS\ABC\ABC.INF /C C:\LOTUS\ABC\CINSTALL.INI /A /O C:\LOTUNIN.LOG /L EN /U NETADMIN To invoke a silent uninstall, add the switch /s to the command line when uninstall is invoked, e.g., C:\WIN95\lunin11.exe /T SmartSuite /V 98.0 /I c:\lotus\suit.inf /C c:\lotus\cinstall.ini /O /L EN /S You can view and change the command line for your Add/Remove item or Uninstall icon, if necessary. You can find the Uninstall command line in the following Registry location: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\ <product name & version>\UninstallString NOTE: Only network administrators should view or change the Uninstall command line. Individual users should run Uninstall from the Control Panel. ----------------------------- 11. Information to Give Users ----------------------------- Provide users with the following information about installing products: * Instructions on how to connect to: - The network - File server directories, such as the Lotus application program, personal, and shared data directories Please keep in mind that if you are not installing to a UNC path, node users must be mapped to all Lotus product and shared tools directories on the file server at the same level in the directory structure as you specify during the file server install. It is a good idea to tell them which drives to map to and provide them with a batch file to connect to these drives. - Network printers, and how to print on a network * Information on using the Lotus Install program * Information on starting Lotus applications * Information on other applications, as required ------------------------- 12. If You Have a Problem ------------------------- PROBLEM: A user cannot run a Lotus application from the assigned node. SOLUTION: Ensure that the user has completed the Install successfully, that the network connections are valid, and that users have read-only access to the program directory. PROBLEM: When selecting the folder to start a Lotus application, a user receives an error message saying the path is invalid or the file is not found. SOLUTION: Check the drive letter specified for the Lotus application folder. To do this: 1. Click Start on the Taskbar. 2. Choose Settings. 3. Choose Taskbar. 4. Select the Start Menu Programs tab. 5. Click Advanced. This loads the Explorer. 6. Under Programs, select the Lotus Node Install. 7. Choose File - Properties. 8. Select the Shortcut tab. 9. Select the appropriate Lotus Application folder. 10. Make sure that the drive letter in the user's network connection to the Lotus program directory is the same as that specified for the Lotus application folder, or change the properties of the folder to use the drive letter specified in the user's network connection. PROBLEM: A user tries to gain access to a shared data file in the shared data directory on the file server and receives a message indicating that no reservation is available. SOLUTION: This problem could be caused by any of the following: * Another user has the file reservation. * The directory is a read-only directory and does not allow users to write to files. * The file is a read-only file. ---------------------------------------- 13. Network-Specific Information for Organizer 6.0 ---------------------------------------- Artisoft LANtastic versions 6.0 and 7.0 --------------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory Organizer program directory recommended shared name - ORGANIZE access - read (R) Lotus Shared Tools directory recommended share name - COMPNENT access - read (R) NOTE: After installing Organizer, users will not be able to use Organizer unless you make each file in the Lotus Shared Tools directory a read-only file. To do so, use the DOS ATTRIB command. Banyan VINES versions 5.5x and 6.0 ---------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory Organzier program directory recommended StreetTalk item name - ORGANIZE@GROUP@ORGANIZATION access - read (R) Lotus Shared Tools directory recommended StreetTalk item name - COMPNENT@GROUP@ORGANIZATION access - read (R) NOTE: After installing Organizer, users will not be able to use it unless you make each file in the Lotus Shared Tools directory a read-only file. To do so, use the DOS ATTRIB command. DEC PATHWORKS version 5.1 and later ----------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory Organizer program directory recommended application file service name - ORGANIZE access - read (R) Lotus Shared Tools directory recommended application file service name - COMPNENT access - read (R) OS/2 LAN Server version 4.0 and IBM Warp Server ----------------------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory Organizer program directory recommended alias - ORGANIZE access - read (R) Lotus Shared Tools directory recommended alias - COMPNENT access - read (R) Microsoft Windows NT Server, version 3.51 or later -------------------------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory Organizer program directory recommended share name - ORGANIZE access - read (R) Lotus Shared Tools directory recommended share name - COMPNENT access - Read (R) Novell NetWare versions 3.x and 4.1 ----------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory Organizer program directory access - Read-File Scan (RF) Lotus Shared Tools directory access - Read-File Scan (RF) ------------------------ 14. Multilingual Install ------------------------ Overview -------- In this release, you can install copies of Organizer in multiple languages. This capability is part of the Lotus strategy for multilingual computing. You install each language version into the same product directory. This provides a large savings of disk space since only the differences between language versions take up additional space. Separate language subdirectories will automatically be created for files which are language specific such as SmartMasters, Install files, etc. Once you have mulitiple language versions of Organizer installed, you can easily choose which language version you want to run when you start the application. (Note that in this release, Asian language versions of Organizer do not support multilingual installations.) In a server install, you must install the additional language(s) into the same directory with the primary language version of Organizer. Additionally, you must select the same Install Option for each language. For example, if you select "Default Features" for the first language, you must select "Default Features" for each subsequent language. If you select "Customize Features" you must turn all product features on in the Customize tabs in both the first language install and all subsequent language installs. If you install additional languages as part of the same copy of Organizer on the server the first language you install becomes the default language. Install generates one install directory, one node install executable, and one icon for each language. Then the node user clicks on the icon for the language they want to install next. Additional language node copies of Organizer can be installed into existing personal directories for Organizer on node machines. The first language you install to a node becomes the default language. To add an additional language version of a Lotus application, the user must rerun the Install program from the appropriate language subdirectory on the server. The Install program informs the user that they already have a copy of the product in a different language, and preserves the directory structure of the default language. The Install program populates the Start Menu with icons for the additional languages of Organizer. These icons can be identified by the two character ISO language tag. For example, the icon for the French version of Organizer is labeled Organizer - FR. Like node installs, additional language standard installs can only be made to one copy of the product; they cannot be installed in different places on the same machine. Additionally, you must select the same Install Option for all languages. For example, you can choose "Default features" each time you do an installation, or "Minimum features" for all installations, or if you choose "Customize features" you must select all features via the Customize dialog boxes. Performing a server install from CD or diskette ------------------------------------------------- To install an additional language: 1. Install a copy of Organizer on the server. 2. Run the Install program from the CD or diskettes for the additional language version of Organizer. 3. Choose the same drives and directories you chose the first language. Install will create a language subdirectory for each additional language you install. 4. Inform your node users where they can find the icon for the language(s) they want to install.